Skip to content

Point monthly review at CryptoCodexAuditBridge#59

Merged
Pigbibi merged 1 commit into
mainfrom
codex/rename-crypto-bridge-target
May 23, 2026
Merged

Point monthly review at CryptoCodexAuditBridge#59
Pigbibi merged 1 commit into
mainfrom
codex/rename-crypto-bridge-target

Conversation

@Pigbibi

@Pigbibi Pigbibi commented May 23, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

@Pigbibi Pigbibi merged commit e23e43b into main May 23, 2026
1 check passed
@Pigbibi Pigbibi deleted the codex/rename-crypto-bridge-target branch May 23, 2026 13:04

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 362509d33c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

owner: ${{ github.repository_owner }}
repositories: |
SelfHostedCodexAuditBridge
CryptoCodexAuditBridge

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Derive app token repo from configured target repository

TARGET_REPOSITORY is configurable via SELFHOSTED_CODEX_REVIEW_REPOSITORY, but the app-token step now hardcodes CryptoCodexAuditBridge. In environments that still set SELFHOSTED_CODEX_REVIEW_REPOSITORY to another repo (for example the previous SelfHostedCodexAuditBridge value), the dispatch call targets that repo while the GitHub App token is scoped to a different repo, causing 403/404 on POST /dispatches unless a fallback PAT is present. This regression was introduced by changing only the token scope constant, so the token scope should be computed from the same configured target repository.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant